|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.05 13:48:00 -
[1]
Coming back from a 9 month EVE break and it's nice to see that EMMA is just as useful now as it was then. And still being developed.
I know the NAV report has always been a bit of an issue and I understand something of why it's a difficult problem, but I am seeing a couple of things in the NAV report this time that should be easy(ish) to chase down and fix.
1) The report group includes my trading corp as well as my trading characters and the wallet balance for the corporation is also being reported as the wallet balance for the corp CEO, thus being double counted in the overall total.
2) Sell orders on behalf of the corporation are being double-counted; that is they're reported as assets both for the corporation and for the character that put them up.
Thanks.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.07 10:16:00 -
[2]
Originally by: Lost Hamster
Originally by: Anna Weston
...
Can you confirm that you are using the version: 1.4.1.5 ? As the problems what you are reporting are fixed by now.
Got the auto-update to 1.4.2.1 yesterday, and that did seem to fix it.
Thanks again. |

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.25 15:18:00 -
[3]
Edited by: Anna Weston on 25/07/2010 15:19:08 Beta test report
So I downloaded the beta last night, but wimped out and kept my old database for the moment. The API update status shows a constant error for Corporation Orders, and I get the following exception reports.
===================================================================================== EXCEPTION REPORT ===================================================================================== 25/07/2010 16:08:46 Error - EveMarketMonitorApp.Common.EMMAException - Error when adding market orders from api Inner Exception: Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. Stack Trace: at System.Data.DataTable.EnableConstraints() at System.Data.DataTable.set_EnforceConstraints(Boolean value) at System.Data.DataTable.EndLoadData() at System.Data.Common.DataAdapter.FillFromReader(DataSet dataset, DataTable datatable, String srcTable, DataReaderContainer dataReader, Int32 startRecord, Int32 maxRecords, DataColumn parentChapterColumn, Object parentChapterValue) at System.Data.Common.DataAdapter.Fill(DataTable[] dataTables, IDataReader dataReader, Int32 startRecord, Int32 maxRecords) at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior) at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable) at EveMarketMonitorApp.DatabaseClasses.EMMADataSetTableAdapters.OrdersTableAdapter.FillOrderExists(OrdersDataTable dataTable, Nullable`1 ownerID, Nullable`1 walletID, Nullable`1 stationID, Nullable`1 itemID, Nullable`1 totalVol, Nullable`1 remainingVol, Nullable`1 range, Nullable`1 orderState, Nullable`1 buyOrder, Nullable`1 price, Nullable`1 eveOrderID, Nullable`1& exists, Nullable`1& orderID) at EveMarketMonitorApp.DatabaseClasses.Orders.Exists(OrdersDataTable ordersTable, OrdersRow orderRow, Int32& ID) at EveMarketMonitorApp.AbstractionClasses.APICharacter.RetrieveOrders(CharOrCorp corc, XmlDocument fileXML)
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.26 11:22:00 -
[4]
Originally by: Ambo
Originally by: Anna Weston Edited by: Anna Weston on 25/07/2010 15:19:08 Beta test report
So I downloaded the beta last night, but wimped out and kept my old database for the moment. The API update status shows a constant error for Corporation Orders, and I get the following exception reports.
===================================================================================== EXCEPTION REPORT ===================================================================================== 25/07/2010 16:08:46 Error - EveMarketMonitorApp.Common.EMMAException - Error when adding market orders from api
Interesting, can you give me any extra information? (i.e. is it when you're updating orders for a corp or character. Any idea what the item might be? etc)
OK, the report group consists of two characters and a corporation, both characters are members of the corp. Every time EMMA updates the status update window shows an error for the Corporation Orders and green for every other entry. At every update there are two "Corp market orders CharacterID=xxxxxxxx" xml downloads, and two identical exception reports turn up in ExceptionLog.txt (i.e. the one I posted previously)
Clearly EMMA is failing to load both of the "corp market orders" xml files each update. I did quickly scan through one of them and didn't see any entries that looked obviously anomalous, but then I don't know what constraints the EMMA import routines are setting so it's hard to know where to start looking for the specific item.
Here's the first few lines from one of the xml downloads.
<?xml version="1.0" encoding="UTF-16" standalone="yes"?> <eveapi version="2"> <currentTime>2010-07-26 10:48:11</currentTime> <result> <rowset name="orders" key="orderID" columns="orderID,charID,stationID,volEntered,volRemaining,minVolume,orderState,typeID,range,accountKey,duration,escrow,price,bid,issued"> <row orderID="1138141001" charID="770219797" stationID="60000829" volEntered="200" volRemaining="108" minVolume="1" orderState="3" typeID="2203" range="32767" accountKey="1000" duration="90" escrow="0.00" price="1550.00" bid="1" issued="2009-05-26 13:21:12" />
If one or more of the complete xml files would be useful I'm happy to e-mail them to you (drop me an EVE-Mail if so).
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.28 12:38:00 -
[5]
Nice work.
I've just updated, I'll report back later today.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.07.28 22:37:00 -
[6]
Originally by: Ambo 1.5.1.1 is now available.
This hopefully fixes Anna's issue though I can't be 100% sure as I couldn't reproduce it.
Sorry, nop 
I'm seeing exactly the same errors, and now of course the shiny new asset tracking thingy is deciding that a whole bunch of newly bought items are "found" and that all the sold ones are "destroyed".
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.01 07:52:00 -
[7]
Originally by: Ambo EMMA 1.5.1.2 beta is now available.
I've not been able to reproduce Anna's issue but in the course of investigating it, I've found several problems. In particular, it seems that the corporate orders API does actually return all corporate orders and not just the orders created by that character as I had thought.
Due to this, I've made changes to go back to the old system of only retrieving corporate orders for the selected character.
That does seem to have fixed the problem of corporate orders not updating. However it has led to a return of the infinite-number-of-unacknowledged-orders-to-click-through problem. Overall I'd say it's the lesser of two evils.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.03 13:59:00 -
[8]
Originally by: Ambo
If anyone is still getting any issues with the beta, please let me know so that I can fix them before general release. In particular, the problem with lots of orders needing to be acknowleged. If any of those orders should not be there and have a creation date after 30th July, please give me a shout.
Sorry, but yes. I'm seeing it with orders dated right up to yesterday.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.03 14:09:00 -
[9]
Also, although I haven't been seeing any error messages within the user interface, the exception log shows this for - at first glance - every API update.
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 01:42:03 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== EXCEPTION REPORT ===================================================================================== 01/08/2010 08:40:35 Warning - EveMarketMonitorApp.Common.EMMAException - market order retreived in 'Exists' is not unique. diagnostics follow:
===================================================================================== uh-oh, character limit...
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.05 12:16:00 -
[10]
Hmm.
I tried auto-updating EMMA and it didn't find any new beta updates.
I tried downloading the August 5th update files from EVE Files but Windows doesn't think they're valid zip files. Had this upload gotten corrupted maybe?
|
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.07 13:00:00 -
[11]
Originally by: Ambo 1.5.1.5 Beta is now up.
This contains a fix for the issue that causes corporate orders to keep asking for acknowledgement
Big thanks to Lost Hamster for tracking this bug down for me.
- Version 1.5.1.0 included a change to store corporate orders and assets by the corporation ID rather than the character ID of the character that had been used to retreive the data from the API. Unfortunatley, a bug slipped in that caused an order's owner to be set to the character ID when it was acknowledged. This has now been fixed.
Very nice work again Ambo.
I updated yesterday morning (after removing EVE-files from the update list) and I'm now only getting order acknowledgement requests for orders that have actually been completed. Also no further errors in the Exception Log since the update.
I still am getting a bunch of "item is lost or destroyed" messages for items that were sold through orders but for now I'm assuming these are a hangover from the previous order confusion. If I'm still seeing these next week I'll post an update.
And finally. I'm pretty sure this is an old behaviour (I'm sure I remember it from when I was using EMMA last year) but it's a mild irritation. If I leave EMMA on in the background then I get multiple (duplicate) order acknowledgment windows to click through, possibly one for every API update that happened while EMMA was minimised. This is just a UI niggle but it would be nice if it went away. 
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.11 15:34:00 -
[12]
Nice work and excellent decision to minimise to taskbar. Windows 7 tray icons are a bit annoying to deal with.
One slight problem with the API update display I see is that that there seems to be a slight mismatch between the window content and the window border on the right-hand edge, so that the last few millimetres of text is cut off. This isn't an issue of window size, I can drag the window as wide as I like and the text still refreshes into the same position. Minor really.
And I hope you don't take it the wrong way if I start raising new issues, but I can't help myself while I see how much stuff you're adding and fixing right now!
The Net Asset Value report is theoretically my favourite report as it would be the ideal tool for measuring the progress of my trading business. Except that there always seems to be something funky going on with the numbers somewhere so it's hard to trust the results.
1)Cash in Escrow consistently shows as zero in the most recent period of a NAV for multiple periods, or an all-time NAV report. Earlier periods will show varying amounts for Cash in Escrow, none of them correct and some of them negative.
2) Wallet balances are correct for the most recent period or in an all-time report, but in earlier periods the wallet balances of corp members are always identical to the corp wallet balance.
Historical asset values look very odd as well though right now it's hard for me to see enough of a pattern to make a useful bug report.
Once again, thanks for all your work so far.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.11 20:23:00 -
[13]
Originally by: Ambo No problem.
The NAV report is based a lot on orders so all those duplicate orders you had will be screwing it up right now. Unfortunately, these can't be corrected automatically so you really have 3 choices:
1. Wait for a while and be aware that older nav reports will always be messed up. 2. Try to correct the data manually with something like sql management tool express. 3. Nuke the old database and start from fresh.
I can give you some help with option 2 if you decide to go that way and I'll see if there are different ways I could produce the data but for now, I'm afraid your stuck with it.
Yes, I recognise that problem is always in the background and I've provisionally decided to nuke my database and start again once this beta phase is over.
However, I'm pretty sure the messed up orders don't explain problem 2 and I'm not sure I can see how they explain problem 1. Also, I was testing with a NAV report with 10 daily report periods so the most recent days should be free of the effects of the duplicated orders, no?
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.13 12:08:00 -
[14]
Edited by: Anna Weston on 13/08/2010 12:14:56 *drools*
Edit: Oops, I think you "fixed" the API update status window in the wrong direction. I can't see the timers at all now, in Windows 7.
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.14 18:00:00 -
[15]
Originally by: Ambo 1.5.2.3 beta is up
Will hopefully resolve this layout problem but I can't be sure (since I can't test on win 7 right now)
I'll be away for the next week so hopefully this works. 
Fixed, thanks!
|

Anna Weston
Gallente Holdings Inc
|
Posted - 2010.08.16 11:09:00 -
[16]
Edited by: Anna Weston on 16/08/2010 11:15:15
Originally by: Ambo Corrected a bug in the NAV report that could cause incorrect wallet balances to be reported for characters that were part of corps that were also included in the report group.
Not fixed, sorry. The correct wallet balances are being reported for the current period but for previous periods the character wallet balances are still being reported as the same as the corp wallet balance.
Quote: The 'cash in escrow' part of the NAV report has been revamped and will now be far more accurate.
I think there's something very wrong with the cash in escrow calculations for previous periods; I'm going to wait a couple more days so I've got more data in my now largely empty database and if it's still behaving the same way I'll post an example.
|
|
|
|